Information processing system

ABSTRACT

In a system in which a wireless access network and another network are connected to each other, an accurate fee is charged in a case where data held in an application server disposed in the wireless access network is used. 
     The application server holds an application and data relating to the application. A usage mode information generating unit generates usage mode information which is information relating to a usage mode when the wireless terminal uses the held data. A network data usage amount measuring unit measures a network data usage amount when the wireless terminal uses data on another network via a wireless access network connected to the wireless terminal. A fee charging unit charges a fee on the basis of the measured network data usage amount and charge a fee on a basis of the generated usage mode information.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.16/547,570, filed Aug. 22, 2019, which is a continuation of U.S.application Ser. No. 16/088,447, filed Sep. 26, 2018 (now U.S. Pat. No.10,440,191), which is based on PCT filing PCT/JP2017/008662, filed Mar.6, 2017, and claims priority to JP 2016-085543, filed Apr. 21, 2016, theentire contents of each are incorporated herein by reference.

TECHNICAL FIELD

The present technology relates to an information processing system. Morespecifically, the present technology relates to an informationprocessing system configured to send/receive information using wirelesscommunication.

BACKGROUND ART

A system in which a wireless access network and another network such asthe Internet are connected to each other is conventionally used. Oneexample of such a system is Long Term Evolution (LTE). In LTE, awireless access network and another network are connected to each othervia Evolved Packet Core (EPC), which is a core network. Further, alldata is converted into packets that are based on an internet protocol(IP) and transferred. In such a system, a user who uses a wirelessterminal can use an application provided by the Internet.

As a technology for improving usability when an application on the othernetwork is used from the wireless access network in such a system, therehas been proposed mobile edge computing (MEC). In MEC, a cache serverthat temporarily holds data associated with the application is providedwithin the wireless access network. Accessing the data held in thiscache server can shorten time when transferring data to the wirelessterminal and improve usability.

One proposed technology for the cache server is a system in which alocal cache is provided to a wireless access network, and a fee ischarged when a user uses data held in the local cache (see, for example,Patent Literature 1). In this system, a fee is charged when data such ascontent is provided from the network to the local cache.

CITATION LIST Patent Literature

Patent Literature 1: JP 2015-92748A

DISCLOSURE OF INVENTION Technical Problem

In the above-described conventional technology, a fee is charged whendata is held in the local cache, but a fee is not charged when a useruses the data held in the local cache thereafter. Because of this, thereis a problem in that a fee cannot be correctly charged in a case where,for example, the data held in the local cache of the wireless accessnetwork is used a plurality of times, and the like.

The present technology has been developed in light of such a problem andhas an object to charge a fee according to a usage amount of data heldin a cache server provided in a wireless access network.

Solution to Problem

The present technology has been devised to solve the above-describedproblem, and a first aspect thereof is an information processing system,including: an application server configured to hold an application anddata relating to the application; a usage mode information generatingunit configured to generate usage mode information which is informationrelating to a mode of use when the wireless terminal uses the held data;a network data usage amount measuring unit configured to measure anetwork data usage amount when the wireless terminal uses data of aserver on another network via a wireless access network connected to thewireless terminal; and a fee charging unit configured to charge a fee ona basis of the measured network data usage amount and charge a fee on abasis of the generated usage mode information. This configurationresults in an action of charging a fee on the basis of usage modeinformation.

In addition, according to this first aspect, the usage mode informationgenerating unit may generate information indicating that the data heldin the application server is being used as the usage mode information.This configuration results in an action of charging a fee in a casewhere data held in an application server is used.

In addition, according to this first aspect, the fee charging unit maycharge a fee using a rate lower than a rate when the wireless terminaluses data on another network in a case where information indicating thatthe data held in the application server is being used is generated asthe usage mode information. This configuration results in an action ofcharging a fee using a low rate when data held in an application serveris used.

In addition, according to this first aspect, the usage mode informationgenerating unit may generate information indicating that data is beingtransferred to the application server as the usage mode information.This configuration results in an action of charging a fee in a casewhere data is transferred to an application server.

In addition, according to this first aspect, the fee charging unit maycharge a fee using a rate with a negative value in a case whereinformation indicating that data is being transferred to the applicationserver is generated as the usage mode information. This configurationresults in an action of a charging a fee using a rate with a negativevalue in a case where data is transferred to an application server.

In addition, according to this first aspect, the usage mode informationgenerating unit may generate a continuous period of time after startupof the held application as the usage mode information. Thisconfiguration results in an action of a charging a fee according to acontinuous period of time after startup of an application executed in anapplication server.

In addition, according to this first aspect, the fee charging unit maycharge a fee using a rate that is changed according to a continuousperiod of time after startup of the application in a case where acontinuous period of time after startup of the application is generatedas the usage mode information. This configuration results in an actionof a changing a rate according to a continuous period of time afterstartup of an application.

In addition, according to this first aspect, the usage mode informationgenerating unit may generate a number of handover occurrences as theusage mode information. This configuration results in an action ofcharging a fee according to a number of handover occurrences.

In addition, according to this first aspect, the usage mode informationgenerating unit may generate information indicating that the applicationand the data held in the application server have not been used for apredetermined period of time as the usage mode information. Thisconfiguration results in an action of charging a fee in a case where anapplication or the like executed in an application server is not usedfor a predetermined period of time.

In addition, according to this first aspect, the fee charging unit mayinclude a network data remaining balance management unit configured tomanage a remaining balance of a usage fee paid in advance by a user ofthe wireless terminal according to fee charging based on the measurednetwork data usage amount, a data remaining balance management unitconfigured to manage a remaining balance of the usage fee according tofee charging based on the generated usage mode information, and a feecharging management unit configured to determine the usage fee for theuser on a basis of respective remaining balances managed by the networkdata remaining balance management unit and the data remaining balancemanagement unit. This configuration results in an action of managing aremaining balance using a network data remaining balance management unitand a data remaining balance management unit.

In addition, a second aspect of the present technology is an informationprocessing system, including: an application server configured to holdan application and data relating to the application; a usage modeinformation generating unit configured to generate usage modeinformation which is information relating to a mode of use when thewireless terminal uses the held data; a network data usage amountmeasuring unit configured to measure a network data usage amount whenthe wireless terminal uses data on another network via a wireless accessnetwork connected to the wireless terminal; a network data fee chargingunit configured to charge a fee on a basis of the measured network datausage amount; and a fee charging unit configured to charge a fee on abasis of the generated usage mode information. This configurationresults in an action of charging a fee using a network data fee chargingunit and a data fee charging unit.

In addition, according to this second aspect, the data fee charging unitmay be provided for each of a plurality of the application servers andcharge a fee for each of the plurality of application servers. Thisconfiguration results in an action of charging a fee for eachapplication server using a plurality of data fee charging units.

Advantageous Effects of Invention

The present technology can provide a superior effect of correctlycharging a fee relating to the use of data held in a cache serverprovided in a wireless access network. Note that the effects describedherein are not necessarily limitative and may refer to any one of theeffects described in this specification.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is an illustration of an exemplary configuration of aninformation processing system 10 according to a first embodiment of thepresent technology.

FIG. 2 is an illustration of an exemplary configuration of an area forcharging a fee according to the first embodiment of the presenttechnology.

FIG. 3 is an illustration of an exemplary configuration of a feecharging device 260 according to the first embodiment of the presenttechnology.

FIG. 4 is an illustration of an exemplary sequence for setting a usagefee according to the first embodiment of the present technology.

FIG. 5 is an illustration of an exemplary sequence for setting a usagefee according to the second embodiment of the present technology.

FIG. 6 is an illustration of an exemplary sequence for setting a usagefee according to the third embodiment of the present technology.

FIG. 7 is an illustration of an exemplary configuration of a wirelessaccess network 300 according to a fourth embodiment of the presenttechnology.

FIG. 8 is an illustration of an exemplary sequence for setting a usagefee according to the fourth embodiment of the present technology.

FIG. 9 is an illustration of an exemplary sequence for setting a usagefee according to the fifth embodiment of the present technology.

FIG. 10 is an illustration of another exemplary sequence for setting ausage fee according to the fifth embodiment of the present technology.

FIG. 11 is an illustration of an exemplary configuration of a feecharging device 260 according to a sixth embodiment of the presenttechnology.

FIG. 12 is an illustration of an exemplary configuration of an area forcharging a fee according to the seventh embodiment of the presenttechnology.

FIG. 13 is an illustration of an exemplary configuration of a networkdata fee charging device 280 according to the seventh embodiment of thepresent technology.

FIG. 14 is an illustration of an exemplary configuration of a cache datafee charging device 370 according to the seventh embodiment of thepresent technology.

FIG. 15 is an illustration of an exemplary sequence for synchronouscontrol of remaining balances according to the seventh embodiment of thepresent technology.

FIG. 16 is an illustration of an exemplary configuration of aninformation processing system 10 according to a modification example ofan embodiment of the present technology.

MODE(S) FOR CARRYING OUT THE INVENTION

Modes (hereinafter referred to as “embodiments”) for carrying out thepresent technology are described below. Description is given in thefollowing order:

1. First embodiment (example of a case where a fee is charged for use ofdata in an application server)

2. Second embodiment (example of a case where a fee is charged foruploading to an application server)

3. Third embodiment (example of a case where a fee is charged on thebasis of a continuous period of time after startup of an application inan application server)

4. Fourth embodiment (example of a case where a fee is charged on thebasis of number of handover occurrences)

5. Fifth embodiment (example of a case where a fee is charged in a casewhere an application in an application server is not used)

6. Sixth embodiment (example of a case where remaining balances aremanaged by two ABMFs)

7. Seventh embodiment (example of a case where a fee is charged usingtwo fee charging devices)

8. Modification example

1. First Embodiment

[Configuration of Information Processing System]

FIG. 1 is an illustration of an exemplary configuration of aninformation processing system 10 according to a first embodiment of thepresent technology. The information processing system 10 includes anetwork 100, a core network 200 and a wireless access network 300.

The network 100 is a network that sends/receives packets that are basedon an IP such as the Internet. The network 100 includes a server 110that holds an application. This application corresponds to, for example,an application that broadcasts data of images and the like, forinstance.

[Configuration of Core Network]

In FIG. 1, the core network 200 is a network that connects the network100 to the wireless access network 300. EPC, for example, can be used asthe core network 200. The core network 200 includes a home subscriberserver (HSS) 210, a mobility management entity (MME) 240, a packet datanetwork gateway (P-GW) 230, a serving gateway (S-GW) 250, a policy andcharging rule function (PCRF) 220, a fee charging device 260 and abilling domain 270.

The HSS 210 and the MME 240 are connected to each other via an S6ainterface. The MME 240 and the S-GW 250 are connected to each other viaan S11 interface. The S-GW 250 and the P-GW 230 are connected to eachother via an S5 interface. The P-GW 230 and the PCRF 220 are connectedto each other via a Gx interface. In addition, the P-GW 230 and thenetwork 100 are connected to each other via an SGI interface. The PCRF220 and the network 100 are connected to each other via an Rx interface.

The HSS 210 holds subscriber information.

The MME 240 performs processing such as authentication management of awireless terminal 340 that is connected to the wireless access network300 and position management of the wireless terminal 340. The MME 240performs processing on the basis of the subscriber information in theHSS 210.

The S-GW 250 performs relay processing of packets on the basis of thesubscriber information.

The P-GW 230 connects the core network 200 and the network 100 to eachother and controls packets. The P-GW 230 measures a network data usageamount that is a usage amount when a user of the wireless terminal 340uses data of the network 100, for example, data of the server 110 viathe wireless access network 300. As described later, the network datausage amount is measured on the basis of network data fee charginginformation supplied by the PCRF 220. Note that the P-GW 230 is anexample of a network data usage amount measuring unit in the Claims.

The PCRF 220 generates the network data fee charging information anddata fee charging information and supplies this information to the P-GW230 and a fee charging device 260, respectively. Here, the network datafee charging information is information relating to charging a feeaccording to the network data usage amount. The data fee charginginformation is information relating to charging a fee according to ausage amount when the user or the like of the wireless terminal 340 usesdata held in an application server 330 to be described later. Note thatthe usage amount of data held in the application server 330 is referredto as “data usage amount.” A charging rule can be applied to the feecharging information.

The fee charging device 260 charges a fee on the basis of the networkdata usage amount measured by the P-GW 230 and the data usage amountmeasured by the cache data measuring unit 331 to be described later.Note that the fee charging device 260 is an example of a fee chargingunit in the Claims.

The billing domain 270 bills a user who uses the wireless terminal 340for a fee on the basis of a fee charging result from the fee chargingdevice 260.

Details of measuring and charging the usage amount of data in the corenetwork 200 are described later.

[Configuration of Wireless Access Network]

In FIG. 1, the wireless access network 300 includes a base station #1(310), a base station #2 (320), and the application server 330.

The base station #1 (310) and the MME 240 are connected to each othervia an S1-MME interface. In addition, the base station #1 (310) and theS-GW 250 are connected to each other via an S1-U interface. Note thatthe base station #2 (320) is also connected in a similar way via theseinterfaces (not shown). Further, the base station #1 (310) and the basestation #2 (320) are connected to each other via an X2 interface.

The base stations #1 (310) and #2 (320) connect the wireless terminal340 to the wireless access network 300. As illustrated in FIG. 1, thewireless terminal 340 is connected to either the base station #1 (310)or #2 (320) via a Uu interface. Note that while two base stations areprovided in FIG. 1, the present technology is not limited thereto andone base station or three or more base stations may be provided.

The application server 330 is provided for a wireless access network,and holds an application and data relating to the application. Theapplication and the data relating to the application are normally heldin the server 110. If envisioning an application that broadcasts videos,for example, the data corresponds to a video file and using the datacorresponds to an act of downloading the video file. When a userdownloads the video file, the video file is transmitted via a pathway401 represented by the dashed line in FIG. 1. In this case, the timerequired for downloading increases because transmission is carried outvia the P-GW 230 and the S-GW 250.

In order to solve this problem, the video file is held in theapplication server 330 and the video file is downloaded via a pathway402 represented by the broken line in FIG. 1. With this configuration,the time required for downloading can be reduced. In this way, theapplication server 330 holds the data and the held data is used by auser of the wireless terminal 340. Note that one application server 330can be provided for every base station.

In addition, the application server 330 in FIG. 1 includes a cache datameasuring unit 331 and a usage mode information generating unit 332. Thecache data measuring unit 331 measures a data usage amount. An MCEcharging entity (MCE) can be used for the cache data measuring unit 331.The usage amount of data can be measured using the P-GW 230 in a casewhere the user uses the data held in the server 110. In theabove-described example, the usage amount of data when the video file isdownloaded along the pathway 401 can be measured using the P-GW 230.This is because the video file is transmitted via the P-GW 230. However,when the user uses the data held in the application server 330, the P-GW230 is unable to grasp usage of data and cannot perform measurement.

In order to deal with this, the application server 330 measures a usageamount (data usage amount) of data held in the application server 330.Then, a measurement result is sent to the fee charging device 260, tothereby enable a fee to be charged in a case where the data held in theapplication server 330 is used. Before this step, the application server330 sends a fee charging request to the fee charging device 260 andnotifies the fee charging device 260 of start of use of the data held inthe application server 330. Note that embodiments of the presenttechnology are not limited to the configuration in FIG. 1. For example,there can be adopted a configuration in which the application server 330is disposed between the S-GW 250 and the base station #1 (310). Notethat configurations of the cache data measuring unit 331 and the usagemode information generating unit 332 are described in detail later.

[Configuration of Area for Charging a Fee]

FIG. 2 is an illustration of an exemplary configuration of an area forcharging a fee according to the first embodiment of the presenttechnology. FIG. 2 illustrates details of a configuration of a portionin FIG. 1 that is involved with charging a fee.

The P-GW 230 in FIG. 2 includes a policy and charging enforcementfunction (PCEF) 231. The PCEF 231 measures a network data usage amounton the basis of network data fee charging information supplied by thePCRF 220. The network data usage amount can be measured by, for example,measuring the number of packets transmitted via the P-GW 230.

The application server 330 in FIG. 2 includes the cache data measuringunit 331 and the usage mode information generating unit 332.

The cache data measuring unit 331 measures a held data usage amount onthe basis of data fee charging information output from the PCRF 220. Thedata usage amount can be measured by, for example, measuring the numberof packets sent/received between the application server 330 and the basestation 310. The measured data usage amount is sent to the fee chargingdevice 260.

The usage mode information generating unit 332 generates usage modeinformation which is information relating to a mode of use when a useror the like of the wireless terminal 340 uses the data held in theapplication server 330. The usage mode information is sent to the feecharging device 260 together with the above-mentioned data usage amount.The mode of use corresponds to, for example, information indicating thatthe user of the wireless terminal 340 will use the data held in theapplication server 330. In this case, usage mode information is sent tothe fee charging device 260 each time the data held in the applicationserver 330 is used.

The PCRF 220 acquires, as the subscriber information from the HSS 210,information relating to a service permitted by the wireless terminal 340of a subscriber and fee charging for the wireless terminal 340 of thesubscriber. Then, fee charging information is generated on the basis ofthis information. A fee charging rule can be applied to the fee charginginformation. For example, specifying a fee charging method or an ID foridentifying an application, information relating to a flow of data forwhich the data usage amount is to be measured, or the like correspondsto the fee charging information.

The fee can be charged as follows in a case where a user uses the dataof the server 110. First, start information indicating that data usageis to start is sent from an application of the server 110 to the PCRF220. The PCRF 220 generates fee charging information (network data feecharging information) on the basis of the start information and thesubscriber information output from the HSS 210, and supplies the feecharging information to the PCEF 231 of the P-GW 230. After the feecharging information is supplied to the PCEF 231, the PCEF 231 begins tomeasure the network data usage amount. Then, a measurement result issent to the first fee charging device 260 and a fee is charged for theuse of data of the server 110.

On the other hand, the fee can be charged as follows in a case where theuser uses the data of the application server 330. First, startinformation indicating that data usage is to start is sent from theapplication server 330 to the PCRF 220. The PCRF 220 generates feecharging information (data fee charging information) on the basis of thestart information and the subscriber information output from the HSS210, and supplies the fee charging information to the cache datameasuring unit 331. After the fee charging information is supplied tothe cache data measuring unit 331, the cache data measuring unit 331begins to measure the data usage amount. Then, a measurement result issent to the fee charging device 260. In addition, the usage modeinformation generating unit 332 generates usage mode information andsends this information to the fee charging device 260. Thereafter, thefee charging device 260 charges a fee for use of the data held in theapplication server 330.

The measurement of the network data usage amount and the measurement ofthe data usage amount can be performed simultaneously or separatelyaccording to how the data is used. For example, only the network datausage amount is measured in a case where the user of the wirelessterminal 340 uses the data of the server 110. Only the data usage amountis measured in a case where the user of the wireless terminal 340 or abusiness that runs an over-the-top business uploads data to theapplication server 330. In addition, only the data usage amount ismeasured even in a case where the user of the wireless terminal 340sends/receives data relating to an application such as a game to/fromthe application server 330. Both the network data usage amount and thedata usage amount are measured in a case where the user of the wirelessterminal 340 uses the data of the server 110 and that data is held inthe application server 330.

[Configuration of First Fee Charging Device]

FIG. 3 is an illustration of an exemplary configuration of the feecharging device 260 according to the first embodiment of the presenttechnology. A fee charging device 260 in FIG. 3 that performs online feecharging. Herein, “online fee charging” refers to a method of charging afee in which a fee is charged each time a network is used.

The fee charging device 260 includes an account balance managementfunction (ABMF) 261, an online fee charging function (OCF) 262, a ratingfunction (RF) 263 and a fee charging trigger function (CTF) 264.

The ABMF 261 manages a remaining balance of the subscriber. In FIG. 3,the remaining balance of a user of the wireless terminal 340 is managed.Here, “remaining balance” refers to a balance of a network usage feepreviously purchased by the subscriber. The ABMF 261 manages theremaining balance on the basis of a result of fee charging performed bythe OCF 262 to be described later.

The RF 263 determines the rate and outputs the rate to the OCF 262.Here, “rate” refers to a ratio between the usage amount of data and afee and, for instance, corresponds to a usage fee per packet.

The CTF 264 detects occurrence of a paid event. In addition, the CTF 264further includes a function of stopping the subscriber from using thenetwork in a case where the account balance has run out due to using thenetwork.

The OCF 262 controls the entire fee charging device 260 and executesonline fee charging. When usage amounts of data are sent from the P-GW230 and the cache data measuring unit 331, the OCF 262 authenticatesusage of this data. Next, a fee is charged on the basis of the sentusage amounts of data and a rate output from the RF 263. At this time,the OCF 262 further changes a fee charging scheme on the basis of usagemode information sent from the usage mode information generating unit332. Then, a fee charging result is sent to the ABMF 261. In addition,the OCF 262 sends information relating to a remaining balance or thelike managed by the ABMF 261 to the billing domain 270.

Note that when a fee charging request for use of the data in theapplication server 330 is sent, the OCF 262 checks the remaining balanceheld in the ABMF 261 and determines whether or not data can besent/received. Then, an amount of available data (available data amount)can be calculated and sent to the application server 330. In addition, afee can also be determined for the available data amount.

The core network 200 has less load in a case where a user uses data heldin the application server 330 compared to a case where a user uses dataheld in the server 110. This is because there is no need to transferdata via the P-GW 230 and the S-GW 250. Therefore, a low usage fee canbe set in relation to using data this way. In this case, the OCF 262ascertains that the data held in the application server 330 is beingused through the usage mode information sent from the usage modeinformation generating unit 332 and lowers the rate for such use. Withthis configuration, a low usage rate can be set.

[Setting Usage Fee]

FIG. 4 is an illustration of an exemplary sequence for setting a usagefee according to the first embodiment of the present technology. First,the fee charging request and the usage mode information are sent fromthe application server 330 to the OCF 262 (801). An ID for identifyingthe wireless terminal 340 is included in the fee charging request. Inaddition, the usage mode information is information representing use ofthe data held in the application server 330. The OCF 262 that hasreceived the fee charging request and the usage mode informationacquires a remaining balance (802). More specifically, a remainingbalance of the user of the wireless terminal 340 is acquired from theABMF 261. Next, the OCF 262 sends a rate transmission request to the RF263 (803). The RF 263 that has received the rate transmission requestsends a rate to the OCF 262 (804). The OCF 262 that has received therate determines an available data amount and a fee on the basis of theacquired balance and the received rate (805) and sends the availabledata amount to the application server 330 (806). Then, a service isstarted (807) in the application server 330 that has received theavailable data amount, and data use or the like is executed.

In this way, in the first embodiment of the present technology, theusage mode information generating unit 332 generates informationindicating that the data held in the application server 330 is beingused as the usage mode information and a fee is charged on the basis ofthis generated usage mode information. With this configuration, anaccurate fee can be charged for use of data held in an applicationserver.

2. Second Embodiment

In the above-described first embodiment, information indicating that thedata held in the application server 330 is being used is generated asthe usage mode information. In contrast, in a second embodiment of thepresent technology, information indicating that data is being uploadedto the application server 330 is generated as the usage modeinformation. The second embodiment differs from the first embodiment inthat a rate when data is uploaded to the application server 330 ischanged.

[Configuration of Area for Charging a Fee]

In a case where a user or the like of the wireless terminal 340 uploadsdata to the application server 330, the usage mode informationgenerating unit 332 according to the second embodiment of the presenttechnology generates information indicating that data is being uploadedas the usage mode information. In other words, information indicatingthat data is being transferred to the application server 330 isgenerated as the usage mode information. For example, there isenvisioned a case in which a business that runs an over-the-top (OTT)business executes an application in the application server 330 and auser of the wireless terminal 340 uploads useful data relating to theapplication. In this case, in a case where the OTT business financiallycompensates the user of the wireless terminal 340 who uploads the usefuldata, the OTT business can compensate the user by setting the rate as anegative value, for example. In addition, for example, a method can beadopted in which the usage fee is made free by not charging the user afee.

Then, the usage mode information generating unit 332 generates usagemode information indicating that such data is being uploaded and sendsthis information to the fee charging device 260. The OCF 262 of the feecharging device 260 that has received the usage mode information chargesa fee by, for example, setting a rate with a negative value. Byincreasing the remaining balance of the user of the wireless terminal340, the user who uploaded the data can be financially compensated. Notethat in a case where an upper limit is set for the financialcompensation, the upper limit can be set by notifying the applicationserver 330 of an uploadable amount of data

[Setting Usage Fee]

FIG. 5 is an illustration of an exemplary sequence for setting a usagefee according to the second embodiment of the present technology. Notethat processing that is the same as the above-described processing inFIG. 4 is denoted by the same reference signs. First, the fee chargingrequest and the usage mode information are sent from the applicationserver 330 to the OCF 262 (810). The usage mode information isinformation indicating upload of data to the application server 330. TheOCF 262 that has received the fee charging request and the usage modeinformation acquires a remaining balance (802). Next, the OCF 262 sendsa rate transmission request to the RF 263 (803). The RF 263 that hasreceived the rate transmission request sends a rate to the OCF 262(804). The OCF 262 that has received the rate determines the rate and anuploadable amount of data on the basis of the acquired balance and thereceived rate, and also an amount of financial compensation for theuploaded data (811). The determined uploadable amount of data is sent tothe application server 330 (812). Then, a service is started (813) inthe application server 330 that has received the uploadable amount ofdata.

Other components of the information processing system 10 are similar tothe components of the information processing system 10 described in thefirst embodiment of the present technology, and hence a description ofthose components is omitted.

In this way, in the second embodiment of the present technology, theusage mode information generating unit 332 generates informationindicating that data is being uploaded to the application server 330 asthe usage mode information, and a fee is charged on the basis of thegenerated usage mode information. With this configuration, a user whouploads data can be financially compensated.

3. Third Embodiment

In the above-described first embodiment, information indicating that thedata held in the application server 330 is being used is generated asthe usage mode. In contrast, in a third embodiment of the presenttechnology, a continuous period of time after startup of an applicationheld in the application server 330 is generated as the usage mode. Thethird embodiment differs from the first embodiment in that the rate ischanged according to the continuous period of time after startup of theapplication held in the application server 330.

[Configuration of Area for Charging a Fee]

The usage mode information generating unit 332 according to the thirdembodiment of the present technology generates a continuous period oftime after startup of an application held in the application server 330as the usage mode information. The application server 330 is a resourceof a business that operates a network business. In the applicationserver 330, the rate is increased in a case where the user or the OTTbusiness executes an application for a long period of time. With thisconfiguration, long-term use of the application by a user or the likecan be reduced, and assets such as the application server 330 can beused effectively.

The OCF 262 of the fee charging device that has received the continuousperiod of time after startup of the application held in the applicationserver 330 as the usage mode information changes the rate acquired fromthe RF 263 to a higher rate and charges a fee.

[Setting Usage Fee]

FIG. 6 is an illustration of an exemplary sequence for setting a usagefee according to the third embodiment of the present technology. Notethat the processing from 801 to 807 is similar to the above-describedprocessing in FIG. 4, and hence this processing is not described.

After starting the service (807), the fee charging request and the usagemode information are sent from the application server 330 to the OCF 262(820). The usage mode information is a continuous period of time afterstartup of an application relating to the use. The OCF 262 that hasreceived the fee charging request and the usage mode information changesthe rate according to the continuous period of time after startup. Then,the fee is recalculated on the basis of the changed rate and the fee ischanged (821). Thereafter, a new fee is sent to the application server330 as a fee charging response (822).

Other components of the information processing system 10 are similar tothe components of the information processing system 10 described in thefirst embodiment of the present technology, and hence a description ofthose components is omitted.

In this way, in the third embodiment of the present technology, theusage mode information generating unit 332 generates a continuous periodof time after startup of an application as the usage mode informationand charges a fee on the basis of the generated usage mode information.With this configuration, a user or the like who uses an application fora long period of time can be charged a fee that has a high rate.

4. Fourth Embodiment

In the above-described first embodiment, information indicating that thedata held in the application server 330 is being used is generated asthe usage mode. In contrast, in a fourth embodiment of the presenttechnology, movement frequency is generated as the usage mode in a casewhere the wireless terminal 340 uses data in another application serverdue to the wireless terminal 340 moving. The fourth embodiment differsfrom the first embodiment in that a plurality of application servers areprovided, and the rate is changed according to the movement frequency ofthe wireless terminal 340.

[Configuration of Wireless Access Network]

FIG. 7 is an illustration of an exemplary configuration of the wirelessaccess network 300 according to the fourth embodiment of the presenttechnology. FIG. 7 illustrates the configuration of part of the wirelessaccess network 300 in the above-described information processing system10 in FIG. 1. The wireless access network in FIG. 7 differs from theabove-described wireless access network 300 in FIG. 1 in the followingways. The wireless access network 300 in FIG. 7 further includes theapplication server #2 (360) connected to the base station #2 (320). Theapplication server #2 (360) includes a cache data measuring unit 361 anda usage mode information generating unit 362.

In addition, FIG. 8 further illustrates an example of a case wherehandover has occurred. Herein, “handover” refers to a function ofautomatically switching a connected base station in response to movementof the wireless terminal 340 and continuing communication. FIG. 8illustrates an example of a case where the wireless terminal 340 that isconnected to the base station #1 (310) has moved into the cell region ofthe base station #2 (320). At this time, the wireless terminal 340 aftermoving is automatically connected to the base station #2 (320) and cancontinuously communicate data. When handover occurs, in a case where thewireless terminal 340 was using data held in the application server #1(330), the wireless terminal 340 can continuously use the data byconnecting to the application server #2 (360).

[Configuration of Area for Charging a Fee]

The usage mode information generating unit 332 according to the fourthembodiment of the present technology generates movement frequency, whichis a number of times the wireless terminal 340 is handed over, as theusage mode information. Handover causes network load to increase becausethe route changes. To deal with this, the rate is increased for a userwho frequently repeats handover, and hence an appropriate user load canbe requested. Note that the user load can be requested from the OTTbusiness that provides the application to the user.

The OCF 262 of the fee charging device that has received the movementfrequency as the usage mode information changes the rate acquired fromthe RF 263 to a higher rate and charges a fee.

[Setting Usage Fee]

FIG. 8 is an illustration of an exemplary sequence for setting a usagefee according to the fourth embodiment of the present technology. Notethat processing that is the same as the above-described processing inFIG. 4 is denoted by the same reference signs. First, the fee chargingrequest and the usage mode information are sent from the applicationserver 330 to the OCF 262 (830). The usage mode information is themovement frequency of the wireless terminal 340. The OCF 262 that hasreceived the fee charging request and the usage mode informationacquires a remaining balance (802). Next, the OCF 262 sends a ratetransmission request to the RF263 (803). The RF 263 that has receivedthe rate transmission request sends a rate to the OCF 262 (804). The OCF262 that has received the rate determines the fee and an available dataamount on the basis of the acquired balance and the received rate, andalso the movement frequency (831). The determined available data amountis sent to the application server 330 (806). Then, a service is startedin the application server 330 that has received the available dataamount (807).

After starting the service (807), the usage mode information indicatingthe movement frequency is sent from the application server 330 to theOCF 262 together with the fee charging request (832). The OCF 262 thathas received the fee charging request and the usage mode informationchanges the rate according to the movement frequency. Then, the fee isrecalculated on the basis of the changed rate and the fee is changed(833). Thereafter, a new fee is sent to the application server 330 as afee charging response (834).

Note that the first step of sending the fee charging request and theusage mode information (830) in FIG. 8 can also be the above-describedstep in FIG. 4 of sending information indicating use of the data held inthe application server 330 as the usage mode information (801).

Other components of the information processing system 10 are similar tothe components of the information processing system 10 described in thefirst embodiment of the present technology, and hence a description ofthose components is omitted.

In this way, in the fourth embodiment of the present technology, theusage mode information generating unit 332 generates the movementfrequency of the wireless terminal 340 as the usage mode information anda fee is charged on the basis of the generated usage mode information.With this configuration, a high rate can be charged in a case wherehandover is frequently repeated.

5. Fifth Embodiment

In the above-described first embodiment, information indicating thatdata held in the application server 330 is being used is generated asthe usage mode. In contrast, in a fifth embodiment of the presenttechnology, information indicating that an application held in theapplication server 330 has not been used for a predetermined period oftime is generated as the usage mode. The fifth embodiment differs fromthe first embodiment in that a fee is charged even in a case where anapplication held in the application server 330 is not used.

[Configuration of Area for Charging a Fee]

The usage mode information generating unit 332 according to the fifthembodiment of the present technology generates information indicatingthat an application held in the application server 330 has not been usedfor a predetermined period of time as the usage mode information. In acase where the application and data relating to the application held inthe application server 330 are not used, a fee charging request is notsent from the application server 330 and a fee is not charged. However,the usage mode information generating unit 332 generates informationindicating that the application and the data have not been used for apredetermined period of time as the usage mode information and sendsthis information to the fee charging device 260. With thisconfiguration, the user of the wireless terminal 340 or the OTT businesscan be charged a fee. In addition, a non-use period, which is a periodof time in which the application or the like held in the applicationserver 330 is not used, can also be generated as the usage modeinformation. In this case, the rate can be increased according to thenon-use period.

The OCF 262 of the fee charging device that has received, as the usagemode information, the information indicating that the application anddata held in the application server 330 have not been used for apredetermined period of time charges a fee to the user or the like ofthe wireless terminal 340.

[Setting Usage Fee]

FIG. 9 is an illustration of an exemplary sequence for setting a usagefee according to the fifth embodiment of the present technology. Notethat processing that is the same as the above-described processing inFIG. 4 is denoted by the same reference signs. First, the fee chargingrequest and the usage mode information are sent from the applicationserver 330 to the OCF 262 (840). An ID for identifying the applicationor the like is included in the fee charging request. In addition, theusage mode information is information indicating that an application anddata relating to the usage has not been used for a predetermined periodof time. The OCF 262 that has received the fee charging request and theusage mode information acquires a remaining balance (802). Next, the OCF262 sends a rate transmission request to the RF 263 (803). The RF 263that has received the rate transmission request sends a rate to the OCF262 (804). The OCF 262 that has received the rate determines a fee fornon-use (841) and sends the determined fee to the application server 330as a fee charging response (842). An ID that is the same as the IDincluded in the above-mentioned fee charging request is included in thefee charging response.

Further, in a case where the application and data held in theapplication server 330 are not used, a fee is charged by repeatingcommunication between the steps 840 and 842 each time a predeterminedperiod of time elapses.

FIG. 10 is an illustration of another exemplary sequence for setting ausage fee according to the fifth embodiment of the present technology.Note that the processing from 840 to 842 is similar to theabove-described processing in FIG. 9, and hence this processing is notdescribed.

After the fee charging response is sent to the application server 330(842), the fee charging request and the usage mode information are sentfrom the application server 330 to the OCF 262 (843) in a case where theapplication and data held in the application server 330 are still notused. The usage mode information is the non-use period. The OCF 262 thathas received the fee charging request and the usage mode informationchanges the rate according to the non-use period. Then, the fee isrecalculated on the basis of the changed rate and the fee is changed(844). Thereafter, a new fee is sent to the application server 330 as afee charging response (845).

Other components of the information processing system 10 are similar tothe components of the information processing system 10 described in thefirst embodiment of the present technology, and hence a description ofthose components is omitted.

In this way, in the fifth embodiment of the present technology,information indicating that an application or the like is not being usedis generated as the usage mode information and a fee is charged on thebasis of the generated usage mode information. With this configuration,a fee can be charged even in a case where an application or the likeheld in the application server 330 is not used.

6. Sixth Embodiment

In the above-described first embodiment, in the fee charging device 260,one ABMF manages the remaining balances. In contrast, in a sixthembodiment of the present technology, different ABMFs manage a remainingbalance according to usage of network data and manage a remainingbalance according to usage of data held in the application server. Thesixth embodiment differs from the first embodiment in that remainingbalances are separately managed by two ABMFs.

[Configuration of Fee Charging Device]

FIG. 11 is an illustration of an exemplary configuration of a feecharging device 260 according to the sixth embodiment of the presenttechnology. The fee charging device 260 in FIG. 11 differs from theabove-described fee charging device 260 in FIG. 3 in that a first ABMF265 and a second ABMF 266 are provided in place of the ABMF 261.

The first ABMF 265 manages the remaining balance of a usage fee paid inadvance according to charging a fee on the basis of a network data usageamount. Further, the second ABMF 266 manages the remaining balance of ausage fee paid in advance according to charging a fee on the basis ofthe usage mode information. When a data usage amount is sent from theP-GW 230, the OCF 262 charges a fee on the basis of the data usageamount and outputs a fee charging result to the first ABMF 265. Thefirst ABMF 265 manages the remaining balance on the basis of the outputfee charging result. In addition, when a data usage amount is sent fromthe cache data measuring unit 331, the OCF 262 charges a fee on thebasis of the usage fee and outputs a fee charging result to the secondABMF 266. The second ABMF 266 manages the remaining balance on the basisof the output fee charging result. In addition, the OCF 262 determines ausage fee for a user of the wireless terminal 340 on the basis of therespective remaining balances managed by the first ABMF 265 and thesecond ABMF and sends the usage fee to the billing domain 270.

Note that the first ABMF 265 is an example of a network data remainingbalance management unit in the Claims. The second ABMF 266 is an exampleof a data remaining balance management unit in the Claims. The OCF 262is an example of a fee charging management unit in the Claims.

In this way, remaining balances are separately managed by the first ABMF265 and the second ABMF 266 according to usage of network data and usageof data held in the application server 330. In a case where theremaining balance managed by the second ABMF 266 is in deficit, usage ofthe data held in the application server 330 is stopped. Even in such acase, usage of the network data can be continued in a case where theremaining balance managed by the first ABMF 265 is in surplus. Forexample, sending/receiving call data can be continued. With thisconfiguration, usability can be improved.

Other components of the information processing system 10 are similar tothe components of the information processing system 10 described in thefirst embodiment of the present technology, and hence a description ofthose components is omitted.

In this way, in the sixth embodiment of the present technology, twoABMFs separately manage a remaining balance according to usage ofnetwork data and manage a remaining balance according to usage of dataheld in an application server. With this configuration, usability can beimproved.

7. Seventh Embodiment

In the above-described first embodiment, the fee charging device 260charges a fee on the basis of usage of network data and charges a fee onthe basis of usage of data held in the application server 330. Incontrast, in a seventh embodiment of the present technology, there isfurther provided a cache data fee charging device configured to charge afee on the basis of usage of data held in the application server 330.The seventh embodiment differs from the first embodiment in thatdifferent fee charging devices separately charge a fee on the basis ofusage of network data and charge a fee on the basis of usage of dataheld in an application server.

[Configuration of Area for Charging a Fee]

FIG. 12 is an illustration of an exemplary configuration of an area forcharging a fee according to the seventh embodiment of the presenttechnology. The configuration of the area for charging a fee in FIG. 12differs from the above-described configuration of the area for charginga fee in FIG. 2 in the following ways. The configuration of the area forcharging a fee in FIG. 12 includes a network data fee charging device280 in place of the fee charging device 260. In addition, theconfiguration of the area for charging a fee in FIG. 12 further includesan application server #2 (360) connected to a base station #2 (320) andcache data fee charging devices #1 (370) and #2 (380).

The network data fee charging device 280 charges a fee and manages aremaining balance on the basis of a usage amount of network data. Inaddition, the network data fee charging device 280 further manages aremaining balance that reflects a fee charging result by a cache datafee charging device to be described later.

The cache data measuring unit 331 of the application server #1 (330) inFIG. 12 sends a measured data usage amount to the cache data feecharging device #1 (370). In addition, the usage mode informationgenerating unit 332 sends generated usage mode information to the cachedata fee charging device #1 (370).

The application server #2 (360) includes a cache data measuring unit 361and a usage mode information generating unit 362 and sends/receives data(packets) to/from the base station #2 (320). The cache data measuringunit 361 sends a measured data usage amount to the cache data feecharging device #2 (380). In addition, the usage mode informationgenerating unit 362 sends generated usage mode information to the cachedata fee charging device #2 (380).

The cache data fee charging device #1 (370) charges a fee for usage orthe like of data held in the application server #1 (330). Morespecifically, a fee is charged on the basis of a data usage amount sentfrom the cache data measuring unit 331 and the usage mode informationsent from the usage mode information generating unit 332.

The cache data fee charging device #2 (380) charges a fee for usage orthe like of data held in the application server #2 (360). Morespecifically, a fee is charged on the basis of a data usage amount sentfrom the cache data measuring unit 361 and the usage mode informationsent from the usage mode information generating unit 362.

In this way, in the seventh embodiment of the present technology, onecache data fee charging device is provided for every application server.A fee is charged on the basis of the data usage amount of eachapplication server through providing the plurality of cache data feecharging devices. Because fee charging and remaining balance managementare performed separately by the plurality of cache data fee chargingdevices and network data fee charging devices, fee charging processingcan be dispersed. At this time, because the remaining balances areseparately managed by the plurality of fee charging devices, theremaining balances need to be synchronized.

[Configuration of Network Data Fee Charging Device]

FIG. 13 is an illustration of an exemplary configuration of a networkdata fee charging device 280 according to the seventh embodiment of thepresent technology. The network data fee charging device 280 includes asynchronization control unit 287, an ABMF 288, an OCF 282, an RF 283 anda CTF 284.

The ABMF 288 manages a remaining balance according to fee charging basedon the network data usage amount. In addition, the ABMF 288sends/receives remaining balance synchronization information which isinformation for synchronizing remaining balances using thesynchronization control unit 287. The remaining balance synchronizationinformation is sent/received to/from an ABMF 378 of a cache data feecharging device 370 using the synchronization control unit 287 and asynchronization control unit 377 of the cache data fee charging device370 to be described later.

The synchronization control unit 287 sends/receives the above-describedremaining balance synchronization information.

The OCF 282 charges a fee on the basis of the network data usage amountsent from the P-GW 230.

The configurations of the RF 283 and the CTF 284 are similar to those ofthe above-described RF 263 and CTF 264 in FIG. 3, and hence theseconfigurations are not described.

Note that the network data fee charging device 280 is an example of anetwork data fee charging unit in the Claims.

[Configuration of Cache Data Fee Charging Device]

FIG. 14 is an illustration of an exemplary configuration of the cachedata fee charging device 370 according to the seventh embodiment of thepresent technology. The cache data fee charging device 370 includes thesynchronization control unit 377, the ABMF 378, an OCF 372, an RF 373and a CTF 374.

The ABMF 378 manages a remaining balance according to fee charging basedon the data usage amount. In addition, the ABMF 378 sends/receivesremaining balance synchronization information using the synchronizationcontrol unit 377.

The synchronization control unit 377 sends/receives the above-describedremaining balance synchronization information.

The OCF 372 charges a fee on the basis of the network data usage amountand the usage mode information sent from the application server 330.

The configurations of the RF 373 and the CTF 374 are similar to those ofthe above-described RF 263 and CTF 264 in FIG. 3, and hence theseconfigurations are not described.

The configuration of the cache data fee charging device 380 is similarto that of the above-described cache data fee charging device 370, andhence the configuration is not described. Note that the cache data feecharging devices 370 and 380 are examples of a data fee charging unit inthe Claims.

[Synchronizing Remaining Balances]

The respective remaining balances managed by the above-described ABMF288 and ABMF 378 in FIG. 13 can be synchronized in the following way.The ABMF 378 of the cache data fee charging device 370 sends theremaining balance managed by the ABMF 378 as the remaining balancesynchronization information to the ABMF 288. In addition, the ABMF 378can acquire a data usage amount from the OCF 372 and send the data usageamount as the remaining balance synchronization information. In a casewhere a number of packets is measured as the data usage amount, themeasured number of packets can be sent as the remaining balancesynchronization information. In a case where the managed remainingbalance is in surplus, the number of packets can be sent as theremaining balance synchronization information after a certain number ofpackets have been accumulated.

On the other hand, the ABMF 288 of the network data fee charging device280 manages a balance according to fee charging based on the networkdata usage amount and also adjusts the remaining balance managed by theABMF 288 on the basis of the remaining balance synchronizationinformation sent from the ABMF 378, and updates the remaining balance.Thereafter, the updated remaining balance is sent to the ABMF 378 as theremaining balance synchronization information. The ABMF 378 that hasreceived the remaining balance synchronization information manages thereceived remaining balance as a new remaining balance.

[Synchronization Control Sequence for Remaining Balances]

FIG. 15 is an illustration of an exemplary sequence for synchronouscontrol of remaining balances according to the seventh embodiment of thepresent technology. FIG. 15 illustrates synchronization control ofremaining balances between the network data fee charging device 280 andthe cache data fee charging device 370. First, a rate is sent from theABMF 288 of the network data fee charging device 280 (850). Next, anumber of packets is sent from the ABMF 378 of the cache data feecharging device 370 as remaining balance synchronization information(851). On the basis of the sent number of packets, the remaining balancein the ABMF 288 of the network data fee charging device 280 is updated(852). Then, the ABMF 288 of the network data fee charging device 280sends the updated remaining balance to the ABFM 378 of the cache datafee charging device 370 as the remaining balance synchronizationinformation (853). The ABMF 378 of the cache data fee charging device370 uses the sent remaining balance to update the remaining balancemanaged by the ABMF 378 (854).

The remaining balances can be synchronized by sending/receiving theremaining balance information. The frequency of sending/receiving theremaining balance information can be determined on the basis of theremaining balances. For example, in a case where the remaining balancesare in surplus, the frequency of sending/receiving the remaining balanceinformation is made relatively low to reduce processing load. In a casewhere a remaining balance runs low, the frequency of sending/receivingthe remaining balance information is made relatively high. This is foraccurately grasping the time at which a balance runs out and quicklystopping the user from using the data or the like.

In this way, in the seventh embodiment of the present technology, onecache data fee charging device is provided for each application serverand remaining balances are managed according to usage of data held in anapplication server. With this configuration, the management of remainingbalances can be dispersed and the load of managing remaining balances inthe core network 200 can be reduced.

8. Modification Example

In the above-described embodiment, data is transmitted to theapplication server 330 via the P-GW 230 and the S-GW 250. In contrast, amodification example of the embodiment of the present technology differsfrom the first embodiment in that the application server 330 isconnected to the network 100 via a dedicated P-GW and S-GW and data istransmitted using the P-GW.

[Configuration of Wireless Access Network]

FIG. 16 is an illustration of an exemplary configuration of theinformation processing system 10 according to the modification exampleof the embodiment of the present technology. The information processingsystem 10 in FIG. 10 differs from the above-described informationprocessing system 10 in FIG. 1 in that the information processing system10 further includes a P-GW 430 and a S-GW 450. The configuration of P-GW430 and the S-GW 450 is similar to the configuration of the P-GW 230 andthe S-GW 250 illustrated in FIG. 2, and hence a description of theconfiguration is omitted.

In the application server 330 in FIG. 16, data is sent from the server110 via the P-GW 430 and the S-GW 450. Also in FIG. 16, the applicationserver 330 generates the usage mode information and sends the usage modeinformation to the fee charging device 260. The fee charging device 260charges a fee on the basis of the sent usage mode information.

In this way, according to the modification example of the embodiment ofthe present technology, a fee can be charged on the basis of the usagemode of the data using a dedicated P-GW 430 or the like for theapplication server 330, even in a case where data is transmitted to theapplication server 330 and held in the application server 330.

As described above, according to the embodiments of the presenttechnology, an accurate fee can be charged for usage of data or the likeheld in an application server by charging a fee on the basis of usagemode information generated by a usage mode information generating unit.

The above-described embodiments are examples for embodying the presenttechnology, and matters in the embodiments each have a correspondingrelationship with disclosure-specific matters in the claims. Likewise,the matters in the embodiments and the disclosure-specific matters inthe claims denoted by the same names have a corresponding relationshipwith each other. However, the present technology is not limited to theembodiments, and various modifications of the embodiments may beembodied in the scope of the present technology without departing fromthe spirit of the present technology.

The processing sequences that are described in the embodiments describedabove may be handled as a method having a series of sequences or may behandled as a program for causing a computer to execute the series ofsequences and recording medium storing the program. As the recordingmedium, a CD (Compact Disc), an MD (MiniDisc), and a DVD (DigitalVersatile Disc), a memory card, and a Blu-ray disc (registeredtrademark) can be used.

Note that the effects described in the present specification are notnecessarily limited, and any effect described in the present disclosuremay be exhibited.

Additionally, the present technology may also be configured as below.

(1)

An information processing system, including:

an application server configured to hold an application and datarelating to the application;

a usage mode information generating unit configured to generate usagemode information which is information relating to a mode of use when thewireless terminal uses the held data;

a network data usage amount measuring unit configured to measure anetwork data usage amount when the wireless terminal uses data onanother network via a wireless access network connected to the wirelessterminal; and

a fee charging unit configured to charge a fee on a basis of themeasured network data usage amount and charge a fee on a basis of thegenerated usage mode information.

(2)

The information processing system according to (1), in which the usagemode information generating unit generates information indicating thatthe data held in the application server is being used as the usage modeinformation.

(3)

The information processing system according to (2), in which the feecharging unit charges a fee using a rate lower than a rate when thewireless terminal uses data on another network in a case whereinformation indicating that the data held in the application server isbeing used is generated as the usage mode information.

(4)

The information processing system according to (1), in which the usagemode information generating unit generates information indicating thatdata is being transferred to the application server as the usage modeinformation.

(5)

The information processing system according to (4), in which the feecharging unit charges a fee using a rate with a negative value in a casewhere information indicating that data is being transferred to theapplication server is generated as the usage mode information.

(6)

The information processing system according to (1), in which the usagemode information generating unit generates a continuous period of timeafter startup of the held application as the usage mode information.

(7)

The information processing system according to (6), in which the feecharging unit charges a fee using a rate that is changed according to acontinuous period of time after startup of the application in a casewhere a continuous period of time after startup of the application isgenerated as the usage mode information.

(8)

The information processing system according to (1), in which the usagemode information generating unit generates a number of handoveroccurrences as the usage mode information.

(9)

The information processing system according to (1), in which the usagemode information generating unit generates information indicating thatthe application and the data held in the application server have notbeen used for a predetermined period of time as the usage modeinformation.

(10)

The information processing system according to (1), in which the feecharging unit includes

a network data remaining balance management unit configured to manage aremaining balance of a usage fee paid in advance by a user of thewireless terminal according to fee charging based on the measurednetwork data usage amount,

a data remaining balance management unit configured to manage aremaining balance of the usage fee according to fee charging based onthe generated usage mode information, and

a fee charging management unit configured to determine the usage fee forthe user on a basis of respective remaining balances managed by thenetwork data remaining balance management unit and the data remainingbalance management unit.

(11)

An information processing system, including:

an application server configured to hold an application and datarelating to the application;

a usage mode information generating unit configured to generate usagemode information which is information relating to a mode of use when thewireless terminal uses the held data;

a network data usage amount measuring unit configured to measure anetwork data usage amount when the wireless terminal uses data onanother network via a wireless access network connected to the wirelessterminal;

a network data fee charging unit configured to charge a fee on a basisof the measured network data usage amount; and

a fee charging unit configured to charge a fee on a basis of thegenerated usage mode information.

(12)

The information processing system according to claim 11, in which thedata fee charging unit is provided for each of a plurality of theapplication servers and charges a fee for each of the plurality ofapplication servers.

REFERENCE SIGNS LIST

-   10 information processing system-   100 network-   110 server-   200 core network-   210 home subscriber server (HSS)-   220 policy and charging rule function (PCRF)-   230, 430 packet data network gateway (P-GW)-   231 policy and charging enforcement function (PCEF)-   240 mobility management entity (MME)-   250, 450 serving gateway (S-GW)-   260 fee charging device-   261, 288, 378 account balance management function (ABMF)-   262, 282, 372 online charging function (OCF)-   263, 283, 373 rating function (RF)-   264, 284, 374 charging trigger function (CTF)-   265 first ABMF-   266 second ABMF-   270 billing domain-   280 network data fee charging device-   287, 377 synchronization control unit-   300 wireless access network-   310, 320 base station-   330, 360 application server-   331, 361 cache data measuring unit-   332, 362 usage mode information generating unit-   340 wireless terminal-   370, 380 cache data fee charging device

The invention claimed is:
 1. An entity to count the number of packets,the entity comprising: circuitry configured to: count the number ofpackets, which are sent from or to an application server for edgecomputing, the number of counted packets are used for charging for anapplication using edge computing, wherein the application server foredge computing is close to a wireless access network that connects witha wireless terminal, generate usage mode information regarding theapplication using edge computing, and send the usage mode informationand the number of counted packets to a charging node, wherein the usagemode information and the number of counted packets are used by thecharging node to perform charging for the application using edgecomputing, wherein the charging node is configured to charge a first feewhen the usage mode information indicates that the wireless terminal isnot using edge computing, and wherein the charging node is configured tocharge a second fee when the usage mode information indicates that thewireless terminal is using edge computing.
 2. The entity to count thenumber of packets according to claim 1, wherein the usage modeinformation regarding the application using edge computing is at leastone of: information regarding data stored by the application server foredge computing and used by the wireless terminal, or informationregarding data uploaded to the application server for edge computingfrom the wireless terminal.
 3. A method for an entity to count thenumber of packets, the method comprising: counting the number ofpackets, which are sent from or to an application server for the edgecomputing, the number of counted packets are used for charging for anapplication using edge computing, wherein the application server foredge computing is close to a wireless access network that connects witha wireless terminal, generating usage mode information regarding theapplication using edge computing, and sending the usage mode informationand the number of counted packets to a charging node, wherein the usagemode information and the number of counted packets are used by thecharging node to perform charging for the application using edgecomputing, wherein the charging node is configured to charge a first feewhen the usage mode information indicates that the wireless terminal isnot using edge computing, and wherein the charging node is configured tocharge a second fee when the usage mode information indicates that thewireless terminal is using edge computing.
 4. The method according toclaim 3, wherein the usage mode information regarding the applicationusing edge computing is at least one of: information regarding datastored by the application server for edge computing and used by thewireless terminal, or information regarding data uploaded to theapplication server for edge computing from the wireless terminal.